Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GEODE-9463: Add SerializableRegionRedundancyStatusImpl to accept list #6753

Merged
merged 1 commit into from
Aug 11, 2021

Conversation

pivotal-eshu
Copy link
Contributor

  • SerializableRegionRedundancyStatusImpl is stored in RegionOperationStateStore region as
    part of OperationState used for REST client.
  • OperationState implements Serializable, which causes it to be serialized as a java
    Serialiable and also nested SerializableRegionRedundancyStatusImpl.
  • Ideally OperationState should implement DSFID to avoid this issue, however, it has been
    released already. So we will add SerializableRegionRedundancyStatusImpl to the accept list
    to avoid this serialization issue when validate-serializable-objects is set to true.

Co-authored-by: Dan Smith dasmith@vmware.com

Thank you for submitting a contribution to Apache Geode.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

For all changes:

  • Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

  • Has your PR been rebased against the latest commit within the target branch (typically develop)?

  • Is your initial contribution a single, squashed commit?

  • Does gradlew build run cleanly?

  • Have you written or updated unit tests to verify your changes?

  • If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:

Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to dev@geode.apache.org.

   * SerializableRegionRedundancyStatusImpl is stored in RegionOperationStateStore region as
     part of OperationState used for REST client.
   * OperationState implements Serializable, which causes it to be serialized as a java
     Serialiable and also nested SerializableRegionRedundancyStatusImpl.
   * Ideally OperationState should implement DSFID to avoid this issue, however, it has been
     released already. So we will add SerializableRegionRedundancyStatusImpl to the accept list
     to avoid this serialization issue when validate-serializable-objects is set to true.

   Co-authored-by: Dan Smith <dasmith@vmware.com>
Copy link

@aaronlindsey aaronlindsey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for finding the root cause and fixing this issue 👍

Copy link
Contributor

@kirklund kirklund left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved!

@pivotal-eshu pivotal-eshu merged commit 7f98970 into apache:develop Aug 11, 2021
@pivotal-eshu pivotal-eshu deleted the feature/GEODE-9463 branch August 11, 2021 16:03
pivotal-eshu added a commit to pivotal-eshu/geode that referenced this pull request Aug 11, 2021
…apache#6753)

* SerializableRegionRedundancyStatusImpl is stored in RegionOperationStateStore region as
     part of OperationState used for REST client.
   * OperationState implements Serializable, which causes it to be serialized as a java
     Serialiable and also nested SerializableRegionRedundancyStatusImpl.
   * Ideally OperationState should implement DSFID to avoid this issue, however, it has been
     released already. So we will add SerializableRegionRedundancyStatusImpl to the accept list
     to avoid this serialization issue when validate-serializable-objects is set to true.

   Co-authored-by: Dan Smith <dasmith@vmware.com>

(cherry picked from commit 7f98970)
nabarunnag pushed a commit that referenced this pull request Aug 16, 2021
…#6753)

* SerializableRegionRedundancyStatusImpl is stored in RegionOperationStateStore region as
     part of OperationState used for REST client.
   * OperationState implements Serializable, which causes it to be serialized as a java
     Serialiable and also nested SerializableRegionRedundancyStatusImpl.
   * Ideally OperationState should implement DSFID to avoid this issue, however, it has been
     released already. So we will add SerializableRegionRedundancyStatusImpl to the accept list
     to avoid this serialization issue when validate-serializable-objects is set to true.

   Co-authored-by: Dan Smith <dasmith@vmware.com>

(cherry picked from commit 7f98970)
pivotal-eshu added a commit that referenced this pull request Aug 16, 2021
…#6753)

* SerializableRegionRedundancyStatusImpl is stored in RegionOperationStateStore region as
     part of OperationState used for REST client.
   * OperationState implements Serializable, which causes it to be serialized as a java
     Serialiable and also nested SerializableRegionRedundancyStatusImpl.
   * Ideally OperationState should implement DSFID to avoid this issue, however, it has been
     released already. So we will add SerializableRegionRedundancyStatusImpl to the accept list
     to avoid this serialization issue when validate-serializable-objects is set to true.

   Co-authored-by: Dan Smith <dasmith@vmware.com>

(cherry picked from commit 7f98970)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants